-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce managed query execution on Driver level #1330
Conversation
24756ef
to
ff1f4fd
Compare
driver/src/main/java/org/neo4j/driver/ResultTransformerProvider.java
Outdated
Show resolved
Hide resolved
driver/src/main/java/org/neo4j/driver/ResultTransformerProviders.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree on your slack remark this being too many overloads. However, it feels more natural to me not having the transformer as part of the config.
I would most like go with
- Having only
Query
objects in the simple api - Adding
of
method toQuery
class, such asQuery.of(cypher)
andQuery.of(cypher, params)
, so that it is still nicely readable
I don't really understand the "Having a single object that would capture both the collector and the result summary handler." remark, but I feel like I don't want this, it's more cruft.
Oh, adding some heresy… |
e3efcdc
to
d6c0bcc
Compare
0f04c03
to
a08bbb2
Compare
This is a new basic high-level API for executing idempotent queries.
a08bbb2
to
01fccf0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good to me. I like the naming choice.
This is a new basic high-level API for executing idempotent queries.